SNMP Data Formats

Name (1)

■

Integer 0..1000

■

The Alarm/event number as listed by product (usually matches the last digit in the trap OID)

The alarm title.

TextualDescription(2)

■

OCTET STRING 0..200

Summary of the reported issue that is forwarded in the varbinds for the following alarm types:

■

OVOC: acEMSTrapGlobalsTextualDescription

■

SBC: acBoardTrapGlobalsDeviceDescription

■

ARM: acARMTrapGlobalsDeviceDescription

■

Zoom: acZoomTrapGlobalsDeviceDescription

Source (3)

■

OCTET STRING 0..255

■

(Devices + OVOC: currently defined as 0..100)

■

The entity source of the problem, usually in the following format:

✔

Trunk#1

✔

SEM/Link#2

✔

Entity1#x/Entity2#y/Entity3#z

Possible values of sources if applicable to a specific alarm. This value is displayed from the variable-binding tgTrapGlobalsSource.

Severity (4)

■

cleared(0)

■

indeterminate(1)

■

warning(2)

■

minor(3)

■

major(4)

■

critical(5)

Possible severity value . This value is displayed from the variable-binding tgTrapGlobalsSeverity.

UniqID (5)

■

String

■

The running number of alarms since the installation of the OVOC instance.

■

The value of this number should be managed by the system separately for alarms and events.

■

The Live Platform application uses this number to recognize if alarms were missed and to retrieve them using the Carrier-grade system.

■

The forwarded information includes Live Platform alarms sequencing for NMS carrier-grade alarms: where the running number events: always -1

NOTIFICATION-TYPE OID as it appears in the MIB. Corrective Action Possible corrective action when applicable. - 1

Alarm ID

■

Integer 0..32000

The unique database ID index for the alarm in the Live Platform portal database.

Type (6)

■

other(0)

■

communicationsAlarm(1)

■

qualityOfServiceAlarm(2)

■

processingErrorAlarm(3)

■

equipmentAlarm(4)

■

environmentalAlarm(5)

■

integrityViolation(6)

■

operationalViolation(7)

■

physicalViolation(8)

■

securityServiceOrMechanismViolation(9)

■

timeDomainViolation(10)

Alarm type according to ITU X.733 definition. This value is displayed from the variable-binding tgTrapGlobalsType.

ProbableCause (7)

■

other(0)

■

adapterError(1)

■

applicationSubsystemFailure(2)

■

bandwidthReduced(3)

■

callEstablishmentError(4)

■

communicationsProtocolError(5)

■

communicationsSubsystemFailure(6)

■

configurationOrCustomizationError(7)

■

congestion(8)

■

corruptData(9)

■

cpuCyclesLimitExceeded(10)

■

dataSetOrModemError(11)

■

degradedSignal(12)

■

dteDceInterfaceError(13)

■

enclosureDoorOpen(14)

■

equipmentMalfunction(15)

■

excessiveVibration(16)

■

fileError(17)

■

fireDetected(18)

■

floodDetected(19)

■

framingError(20)

■

heatingVentCoolingSystemProblem(21)

■

humidityUnacceptable(22)

■

inputOutputDeviceError(23)

■

inputDeviceError(24)

■

lanError(25)

■

leakDetected(26)

■

localNodeTransmissionError(27)

■

lossOfFrame(28)

■

lossOfSignal(29)

■

materialSupplyExhausted(30)

■

multiplexerProblem(31)

■

outOfMemory(32)

■

ouputDeviceError(33)

■

performanceDegraded(34)

■

powerProblem(35)

■

pressureUnacceptable(36)

■

processorProblem(37)

■

pumpFailure(38)

■

queueSizeExceeded(39)

■

receiveFailure(40)

■

receiverFailure(41)

■

remoteNodeTransmissionError(42)

■

resourceAtOrNearingCapacity(43)

■

responseTimeExecessive(44)

■

retransmissionRateExcessive(45)

■

softwareError(46)

■

softwareProgramAbnormallyTerminated(47)

■

softwareProgramError(48)

■

storageCapacityProblem(49)

■

temperatureUnacceptable(50)

■

thresholdCrossed(51)

■

timingProblem(52)

■

toxicLeakDetected(53)

■

transmitFailure(54)

■

transmitterFailure(55)

■

underlyingResourceUnavailable(56)

■

versionMismatch(57)

■

authenticationFailure(58)

■

breachOfConfidentiality(59)

■

cableTamper(60)

■

delayedInformation(61)

■

denialOfService(62)

■

duplicateInformation(63)

■

informationMissing(64)

■

informationModificationDetected(65)

■

informationOutOfSequence(66)

■

intrusionDetection(67)

■

keyExpired(68)

■

nonRepudiationFailure(69)

■

outOfHoursActivity(70)

■

outOfService(71)

■

proceduralError(72)

■

unauthorizedAccessAttempt(73)

■

unexpectedInformation(74)

Alarm probable cause according to ITU X.733 definition. This value is displayed from the variable-binding tgTrapGlobalsProbableCause.

AdditionalInfo1 (8)

■

OCTET STRING 0..255

■

(Devices + OVOC: currently defined as 0..100)

This field is used by the system to provide additional information regarding the reported alarm/event.

Additional information fields provided by MG application, depending on the specific scenario. These values are displayed from tgTrapGlobalsAdditionalInfo1.

AdditionalInfo2 (9)

■

OCTET STRING 0..255

■

(Devices + OVOC: currently defined as 0..100)

This field is used by the system to provide additional information regarding the reported alarm/event.

Additional information fields provided by MG application, depending on the specific scenario. These values are displayed from tgTrapGlobalsAdditionalInfo2.

AdditionalInfo3 (10)

■

OCTET STRING 0..255

■

This field is used be the system to provide additional information regarding the reported alarm/event

■

The forwarded information is filled in the following format:

GW_IP: <Device IP>, GW_TRAP_ID: <device’s alarm unique ID>

Additional information fields provided by MG application, depending on the specific scenario. These values are displayed from tgTrapGlobalsAdditionalInfo3.

DateAndTime (11)

DateAndTime SNMP Object

The timestamp when the alarm was raised.

SystemSeverity (12)

■

cleared(0)

■

indeterminate(1)

■

warning(2)

■

minor(3)

■

major(4)

■

critical(5)

Each value represents the entire system severity when a specific alarm/event is issued.

Note: This varbind is not sent for system alarms (alarms that were generated by OVOC such as OVOC Disk Space alarm).

Possible severity value . This value is displayed from the variable-binding tgTrapGlobalsSeverity.

DeviceName(13)

■

OCTET STRING 0..255

■

(Devices+ OVOC: currently defined as 0..250)

■

This field should not be filled by any of the products, as its reserved for OVOC when an alarm/event is forwarded.

The information is filled in the following format:

■

Until Version 7.4:

MG Region:<EMS Region Name>, MG Name:<EMS MG Name>

■

Until Version 7.6:

<Entity Type> Name:<Entity Name>, Tenant:<Tenant Name>, Region:<Region Name>

Where entity type can be one of the following:

■

Tenant, Region, Site, Device, Link, System etc.

■

Tenant: <Tenant Name> - exists only when the entity has tenant

■

Region: <Region Name> - exists only when the entity has region

The device entity name as described in the adjacent "Type" column.

DeviceInfo(14)

■

OCTET STRING 0..255

■

(Devices + OVOC: currently defined as 0..100)

■

This field should not be filled by any of the products, as its reserved for OVOC when the alarm/event is forwarded.

The information is filled in the following format:

■

Until Version 7.4:

MG Type: <Device Type>, MG Serial: <primary device serial number>, <secondary device serial number>

<secondary device serial number> is applicable for HA devices only

■

Until Version 7.6:

Device Type: <Device Type>

Empty if entity not a device

The detailed device identifiers.

DeviceDescription(15)

■

OCTET STRING 0..255

■

This field should not be filled by any of the products, as its reserved for OVOC when the alarm/event is forwarded.

The information is filled in the following formats:

■

<Device Description> is filled when an alarm is raised on a Device entity.

■

<SBA Description> is filled when an alarm is raised on the SBA entity (provisioned in the Device details under SBA definition rubric).

■

<External application Description>: is filled when an alarm is raised on the ARM or Zoom entities.

■

<Tenant Description> - is filled when an alarm is raised on a Tenant entity.

■

<Region Description> - is filled when an alarm is raised on a Region entity.

■

<Link Description> - is filled when an alarm is raised on a Link entity.

A free text description field can also be globally configured in the OVOC Server Configuration page (System > Administration > OVOC Server > Configuration) for all OVOC System alarms. This text is then sent to trap destinations in alarm forwarding in the varbind acEMSTrapGlobalsDeviceDescription field for all system alarms. For example, OVOC Disk Space alarm.

Note: The hard-coded text description of the alarm that is sent in the TextualDescription(2) acEMSTrapGlobalsTextualDescription varbind (see above) is a separate description field that is different for each alarm OID.

SystemSerialNumber(16)

From Version 7.6:

OCTET STRING 0..255

The information is filled in the following format:

■

For Stand-alone systems: <Device serial number>

■

For HA Systems: format <device serial #1>_<device serial #2>)

Device Serial Number (displays either 32-bit and 64-bit serial numbers for SBC devices) according to the device's firmware version and configuration settings in the externals/configurationProperties/generalConfig file for the include_serial_string.

Device serial number information as described in the adjacent 'Type" column.